Thy Collector
   |
Posted - 2010.09.07 23:52:00 -
[1]
So... I get this (I think). But it doesn't exactly explain the gate lag. If the CPU was really being overloaded, wouldn't this just backup the queue so that there would be a delay from when grid loaded, but not so long that the request would time out. Correct me if I'm wrong, but aren't all requests sent to the location node put into a queue. Under normal load, the queue is processed relatively quickly so it often takes less than a second for things to complete. If the CPU was being jammed with more requests than could be processed in a normal fashion, wouldn't this just back up the queue and bit, and not cause a complete failure of processing of requests.
I figure that you guys are using a priority queue so that certain requests get placed higher up in the queue than other requests. This seems to make sense until those higher priority requests begin to fill up the queue at an unusually fast rate, and so low priority requests never get taken care of. Could this possible a reason as to why the grid never (or takes forever to load) for everyone jumping in? Are requests such as loading a grid from another system (or other things that would effect us actually loading grid after jumping) being put so far back in the queue relative to other requests that they are just never taken care of and time out?
If so wouldn't it make sense to us some kind of run-time like algorithm so that requests that have been in the queue for too long are forced to the front? E.G. requests must be completed in a certain amount of time, regardless of their original priority.
I ask this because I don't understand why loading grid is never taken care of as that seems to be the biggest issue. Its one thing for the grid to take an extra 10-30 seconds to load and its another thing entirely for the grid to take so long to load that the request times out and then we are left helpless.
Further more, sense those already on grid have much less of in issue are grid requests from those entering a new system less important than those already in system?
I understand that there are also other things that need to be taken care of, such as making sure that their are no unnecessary repeats of requests, especially high priority requests, but if it indeed is the case that some requests are just being pushed back so much that they are never taken care of, it seems that making sure they are processed at all should be a higher priority.
|